Managing virtual machine policy compliance

ABSTRACT

A method for managing virtual machine policy compliance. The method for restoring compliance of a virtual machine found to be non-compliant to a compliance rule may comprise detecting non-compliance of a virtual machine using a compliance agent, detaching the virtual machine from a network, creating a copy of a compliance repository volume, mounting the newly requested disk resource having stored the copy of the compliance repository volume, applying a remediation action to the virtual machine, and triggering by the compliance agent a compliance scan for ensuring that the virtual machine complies to the compliance rule.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of priority to United Kingdom PatentApplication No. GB1311807.0, filing date Jul. 2, 2013, the contents ofwhich are hereby incorporated by reference.

FIELD OF THE INVENTION

The invention relates generally to a method for managing virtual machinepolicy compliance. The invention relates further to a system formanaging virtual machine policy compliance, a computing system, a dataprocessing program, and a computer program product.

BACKGROUND OF THE INVENTION

Cloud computing and virtualization have been playing a key role inrecent years among the technologies adopted in information technologysolutions for designing, maintaining and operating data centers.

As physical servers and workstations, even virtualized computingresources, need to comply with certain company policies regardingsoftware configuration and security, lots of software products andsolutions that help IT administrators to monitor policy compliance ofdata centers are on the market.

Typically, IT administrators, security auditors and other professionalsthat are responsible for policy compliance may receive reports fromthose tools that may highlight the computers which may violate definedcompliance rules or may also highlight some other constraints, so thatthe administrators may take an action to resolve the issue. Typically,the resource that may be marked as not-compliant by the tool with thedefined compliance rules may need to be detached from the companynetwork in order to prevent the diffusion of the problem, like viruses,worms, spyware, etc.

Working with a machine not attached to the company network can be verydifficult and may require IT professionals to physically stand in frontof the failing system and log-in to resolve potential problems.Moreover, patching tools are often centralized in the data center orcompany repositories, and thus not available without a networkconnection.

There are some disclosures related to a method for managing virtualmachine (VM) policy compliance.

Document U.S. Pat. No. 8,234,641 B2 discloses techniques for controllingand managing virtual machines. In one particular embodiment, a systemsmanagement partition is created inside the virtual machine to provide apersistent and resilient storage for management information. The VMmanagement information can be made available for pre-executionprocessing, including policy-based compliance testing.

Document US 2010/0017512 A1 discloses a compliance test, during which anidentified VM image is controlled such that it cannot connect to thenetwork. One or more tests are carried out to determine if the virtualmachine is compliant with one or more predetermined requirements. If aVM is compliant with said one or more predetermined requirements, the VMimage is connected to the network.

However, these solutions have limitations in the way compliancedetection is performed and network connections are handled. Therefore,there is a need for an improved mechanism for restoring compliance of aVM found to be non-compliant.

SUMMARY OF THE INVENTION

This need may be addressed by a method for restoring compliance of avirtual machine found to be non-compliant to a compliance rule, arelated compliance system, a computing system, a data processingprogram, and a computer program product according to the independentclaims.

(1) According to one embodiment, a method for restoring compliance of aVM found to be non-compliant to a compliance rule may be provided. Themethod may comprise, detecting non-compliance of a VM with thecompliance rule using a compliance agent. The compliance agent may bedeployed on the VM. Additionally, the existing VM may be detached ordisconnected from a network. A copy of a compliance repository volume—inparticular, a copy of a compliance repository shared service volume—maybe created. This copy may be available on a newly requested diskresource for the VM. Moreover, the disk resource having stored the copyof the compliance repository volume may be mounted—in particularlogically mounted—to the VM. A remediation action may be applied to theVM using content of the copy of the compliance repository volume forrestoring back compliance of the VM, meaning, reverting it back to acompliant state. Furthermore, another compliance scan may be triggeredby the compliance agent for ensuring that the VM may comply with thecompliance rule.

(10) According to another embodiment, a compliance system for restoringcompliance of a VM found to be non-compliant to a compliance rule may beprovided. The compliance system may comprise a compliance detecting unitadapted for detecting non-compliance of a VM with the compliance ruleusing a compliance agent being deployed on the VM, and a detaching unitadapted for detaching the existing VM from a network. Furthermore, thecompliance system may comprise a copy creation unit adapted for creatinga copy of a compliance repository volume on a newly requested diskresource for the VM, a mounting unit adapted for mounting the diskresource having stored the copy of the compliance repository volume tothe VM, and an applying unit adapted for applying a remediation actionto the VM using content of the copy of the compliance repository volumefor reverting back the VM to a compliant state. Additionally, thecompliance system may comprise a triggering unit adapted for triggeringby the compliance agent a compliance scan for ensuring that the VM maycomply with the compliance rule.

It may be noted that the virtual machine may typically be executed on aserver system in a data center. However, the VM may also be deployed ona personal computing device such as a PC, a tablet or any other mobiledevice.

DETAILED DESCRIPTION

In the context of this description, the following conventions, termsand/or expressions may be used:

The term “compliance” of a computer system or a VM may denote that therelated system may be aligned with a set of rules in terms of itsconfiguration and/or software that may be installed and/or executed. Itmay also concern data access rules, users allowed to access the system,potential malware and/or any other rule ensuring a secure operation ofthe computing system. In this sense, the term non-compliance may denotea status in which the related system may not adhere to any of the one ormore predefined compliance rules. A system may thus be in a compliantstate if the system operates according to the predefined compliancerules.

The term “compliance agent” may denote a set of functions—in particularimplemented in software or hardware—checking features and functions ofthe related system to ensure that the predefined one or more compliancerules are met.

The term “compliance repository volume” may denote a storage volume—inparticular a spinning, magnetic disk or another memory system—e.g., asolid state disk—having stored a version of the VM which may adhere tothe compliance rules. Additional configuration information, likescripts, middleware or application software may also be stored on thecompliance repository volume. Basically, a complete set of a predefinedsoftware stack defining the VM with all its aspects may be availablefrom the compliance repository volume. This may include the VM as abasis but also software applications that may be installed on the VM.

The term “remediation action” may denote one or more actions required tobring the system—in particular the VM—back to a status at which it maybe in accordance with the compliance rules defined, i.e., to a compliantstatus.

The term “storage system” may denote a device being adapted to storedata, e.g., scripts, complete or base VMs, application software and/orany other data. The storage system may comprise a specific storagecontroller which may be part of a host computer or may be deployedstand-alone.

The term “hypervisor” may denote a piece of computer software, firmwareor hardware that may create and run VMs. A computer on which ahypervisor may run one or more VMs may be defined as a host machine.Each VM may be is called “guest machine”. The hypervisor may present theguest operating systems with a virtual operating platform and may manageexecution of the guest operating systems. Multiple instances of avariety of operating systems may share the virtualized hardwareresources. More than one hypervisor may be deployed on one physicalserver.

The proposed method for restoring compliance of a VM found to benon-compliant to a compliance rule may offer a couple of advantages:

The compliance test may be performed using an agent running in a VM.Since more than one VM may run on a hypervisor on a physical hardware,it may be possible to control and supervise compliance according tocompliance rules individually per VM. Remediation actions may bedifferent from VM to VM on the same hypervisor and/or physical hardware.Even if the compliance agent may be corrupted on one VM, the relatedcompliance agents on parallel VMs may still be intact. VMs may also besupervised, i.e., checked for compliance, using different compliancerules.

Additionally, the process of restoring compliance of a VM may becompletely independent of any communication network connection. The VMand its compliance test may be—so to speak—self optimized andindependent of network resources. No downloading of compliance testingsoftware or content via a communication network may be required at all.If non-compliance of a VM may be detected—in particular, by a compliancescan by the compliance agent—the compliance agent may initiate aseparation or detachment of the VM from the network, e.g., an enterpriseor datacenter network. Now, the VM may be a standalone and may repairitself without a requirement to re-install the VM another time. Suchre-instantiation may be typical for state-of-the-art compliance tests.With the here provided method, such a re-instantiation may not longer berequired.

A compliance repository volume, which may be attached to the physicalserver supporting hypervisor and thus related virtual machines via astorage channel, may be copied “on-the-fly”—meaning during operation ofthe VM and its application programs—to a disk resource that may havebeen requested by the compliance agent via the hypervisor. Theadditional disk resource may be available from the storage disk beingattached to the physical hardware on which the VM runs. A storage systemor storage sub-system may perform the copy process. Thus, the copy maybe performed independent from the non-compliant VM. Moreover, thecompliance repository volume may have faced any risk of being corruptedby malware running on the VM. All tests and remediation actions may bebased on using the copy of the compliance repository volume onanother—the newly requested—disk resource. Thus, the proposed method andsystem may bring back the VM to a compliant state without an activeconnection to a network using the agent running on the VM itself, aself-protecting copy of a compliance repository volume, activeremediation actions and a reconnect of the VM to the network. All checksand actions may be performed “live” on the active VM and not before a VMis brought to life, i.e., instantiated, initialized and connected, orshut down. The present disclosure may ensure compliance permanentlythroughout the lifetime of the VM.

Additionally advantageously may be the following aspects: By detachingthe VM from the network during restoring compliance, the risk ofspreading the root cause of the non-compliancy of the VM over thevirtual data center is highly mitigated. The malfunction may stay localand may be repaired fast.

And by attaching the compliance repository to the failing, i.e.non-compliant, VM all centrally available tools and resources needed torestore compliance (software bundles, scripts, etc) are immediatelyavailable. It may not be required to choose and select necessary toolsfrom the “repair shop”, i.e., a repair tool set.

Hence, since the repository is centralized per physical (server) system,only this single instance may have to be maintained for all potentialVMs being deployable on the server when compliance rules are modified.

According to one embodiment, the method may also comprise detaching thedisk resource having stored the copy of the compliance repository volumefrom the virtual machine. Such a detachment may occur after performingthe remediation actions or after triggering the newly performedcompliance scan. This way, it may be ensured that the disk space may nolonger be occupied. It may be released again for other purposes.

According to a further embodiment of the method, the method alsocomprises, removing—in particular deleting—the copy of the compliancerepository volume on the newly requested disk resource. Such a deletionfrom the storage system may release disk space to be used for otherpurposes. It may be performed by the storage system under control of thehypervisor triggered by the compliance agent.

According to just a further embodiment of the method, the removing ofthe copy of the compliance repository volume may comprise releasing—inparticular deleting—the newly requested disk resource. Again, such anaction as part of a clean-up process may free up all no longer requiredresources which may only be required during a process of restoringcompliance of a VM.

According to just another embodiment, the method may also compriseattaching back the virtual machine to the network. After such anoperation, the VM may again be fully functional within the context of adata center. No further bottleneck may be expected. Such a re-attachingback to the computer network may be performed after the compliance scanthat may have been performed after the remediation action. This way, itmay be ensured that only compliant system may be attached to the networkagain. Potential risks due to security breeched or similar may notspread to other systems within a data center.

According to an advanced embodiment of the method, the creation of thecopy of the compliance repository volume may be performed by a storagesystem. And moreover, the storage system may be controlled by thehypervisor. The hypervisor again may be triggered by the complianceagent. Thus, not any outside help and not any network connection may berequired for the VM. Thus, a relatively good degree of system securitymay be achieved. Malware may have little chance to negatively influencethe copying process.

According to a further enhance embodiment of the method, the detachingof the disk resource having stored the copy of the compliance repositoryvolume and/or the removing the copy of the compliance repository volumeand/or the releasing of the newly requested disk resource and/or theattaching back the VM to the network may be performed after applying theremediation action. Hence, the remediation action may be performed usingthe copy of the compliance repository volume and after that the requiredstorage space may be freed-up again.

In one embodiment of the method, the remediation action may be performedby the compliance agent using at least one script and/or at least onesoftware component stored on the copy of the compliance repositoryvolume. In particular, a non-compliant software component of the VM, ora non-compliant software component running as application on the VM maybe removed and/or may be replaced by a corresponding compliant softwarecomponent from the copy of the compliance repository volume.Alternatively, the non-compliant software component may be adjusted,e.g., configuration parameters may be reset or re-aligned, to complyagain with the at least one compliance rule. This way, configurationparameters and software components may be set back to a state which maybe compliant with the compliant rule(s). Alternatively, non-compliant ornot allowed software components or configurations may be replaced,disabled or deleted from the VM.

Furthermore, embodiments may take the form of a computer programproduct, accessible from a computer-usable or computer-readable mediumproviding program code for use, by or in connection with a computer orany instruction execution system. For the purpose of this description, acomputer-usable or computer-readable medium may be any apparatus thatmay contain means for storing, communicating, propagating ortransporting the program for use, by or in a connection with theinstruction execution system, apparatus, or device.

The medium may be an electronic, magnetic, optical, electromagnetic,infrared or a semi-conductor system for a propagation medium. Examplesof a computer-readable medium may include a semi-conductor or solidstate memory, magnetic tape, a removable computer diskette, a randomaccess memory (RAM), a read-only memory (ROM), a rigid magnetic disk andan optical disk. Current examples of optical disks include compactdisk-read only memory (CD-ROM), compact disk-read/write (CD-R/W), DVDand Blu-Ray-Disk.

It should also be noted that embodiments of the invention have beendescribed with reference to different subject-matters. In particular,some embodiments have been described with reference to method typeclaims whereas other embodiments have been described with reference toapparatus type claims. However, a person skilled in the art will gatherfrom the above and the following description that, unless otherwisenotified, in addition to any combination of features belonging to onetype of subject-matter, also any combination between features relatingto different subject-matters, in particular, between features of themethod type claims, and features of the apparatus type claims, isconsidered as to be disclosed within this document.

The aspects defined above and further aspects of the present inventionare apparent from the examples of embodiments to be describedhereinafter and are explained with reference to the examples ofembodiments, but to which the invention is not limited.

BRIEF DESCRIPTION OF THE DRAWINGS

Preferred embodiments of the invention will now be described, by way ofexample only, and with reference to the following drawings:

FIG. 1 shows a block diagram of an embodiment of the method forrestoring compliance of a VM found to be non-compliant.

FIG. 2 shows a block diagram of a potential configuration of ahypervisor, a VM, a compliance agent and a storage system.

FIG. 3 shows a block diagram of the configuration of FIG. 2 with acompliance repository volume attached.

FIG. 4 shows a block diagram of the method according FIG. 1 in moredetail.

FIG. 5 shows an embodiment of a compliance system.

FIG. 6 shows a block diagram of a computing system comprising thecompliance system.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

In the following, a detailed description of the figures will be given.All instructions in the figures are schematic. Firstly, a block diagramof an embodiment of the disclosed method for restoring compliance of aVM found to be non-compliant is given. Afterwards, further embodimentdetails of the method and a compliance system for restoring complianceof a VM found to be non-compliant will be described.

FIG. 1 shows a block diagram of an embodiment of the method forrestoring compliance of a VM found to be non-compliant. As shown in thediagram 100 the method may comprise detecting, 102, non-compliance of aVM with the compliance rule. This may be performed, in particular, by atriggering a compliance scan using a compliance agent being deployed onthe VM. Thus, the compliance agent may be implemented as an applicationprogram running on the VM. The method may also comprise detaching, 104,the existing VM from a network. This may be an active method stepcontrolled by the compliance agent.

Moreover, the method may comprise creating, 106, a copy—in particular,“on the fly”, i.e. during the system being live and active—of acompliance repository volume, in particular, a compliance repositoryshared service volume. Such a volume may be available per physicalserver and may be shared among different VMs on the same physicalsystem. Not any network connection may be required to access thiscompliance repository volume. The copy may be made to a newly requesteddisk resource for the VM. In particular, a storage manager (not shown)controlled by the hypervisor may create, 106, the copying. Thehypervisor may be triggered by the compliance agent.

Additionally, the method may comprise mounting, 108, in particularlogically, the disk resource having stored the copy of the compliancerepository volume to the VM which may not be in the compliant state atthis point in time.

Last but not least, one or more remediation actions may be applied, 110,to the VM using content of the copy of the compliance repository volume.This way, compliance may be restored back to the VM. The content maycomprise scripts, check lists, test rules, predefined remediationactions and/or software bundles required to restore compliance of theVM. The content may be stored on the compliance repository volume.

Moreover, the method may comprise triggering, 112, by the complianceagent, a compliance scan for ensuring that the VM complies with thecompliance rule. This additional compliance scan may be seen as anassurance step of the method. However, this way, it may be achieved thatcompliance may really be restored and not only assumed by running thesoftware on the compliance repository volume. Here, an active testbelongs to the components of the method. Once compliance may berestored, the VM may be attached back to the network.

Optionally, the method may comprise additional steps 114, like cleaningup disk space and connecting the VM back to the network. E.g., thedetaching the disk resource having stored the copy of the compliancerepository volume from the VM may be performed. The removing the copy ofthe compliance repository volume on the newly requested disk resourcemay also be part of the disclosed method.

FIG. 2 shows a block diagram of a potential configuration of ahypervisor 210, 212, a VM 214, 216, 218, a compliance agent 224, 226,228 and storage systems or disk systems 204, 206. A datacenter (notshown) may comprise computer hardware 202 like a server. However, themethod may also be performed on a mobile device or a PC, as mentionedabove. On the hardware one or more hypervisors 210, 212 may be installedand being active as a platform for VMs 214, 216, 218 for hypervisor 210,and VMs 220, 222 for hypervisor 212. As an example, disk systems 204 and206 may be attached to or may be part of the computer hardware.Alternatively, the disk systems may be independently controlled as acomponent of a storage subsystem which may be attachable to the server202 via a dedicated storage channel (storage subsystem and storagechannel not explicitly shown). Disk 208 will be discussed in the contextof FIG. 3.

VM 216—as well as the other VMs (not shown)—may also be connected viaconnection 232 to a network 230, e.g., a datacenter or enterprisenetwork, or a wide area network. The connection may be established viathe computer hardware, as a skilled person would know. On each VM 214,216, 218, a separate compliance agent 224, 226, 228 may be deployedbeside other software programs (not shown). The network 230 may be adedicated communication network.

FIG. 3 shows a block diagram of the configuration of FIG. 2 with acompliance repository volume attached. In case, e.g., compliance agent226 may detect a non-compliance, as discussed in context of FIG. 1, thenetwork connection 232 from FIG. 2 may disappear because of a disconnectof the VM 216 from the network 230. Additionally, the disk 208 which maybe a compliance repository volume, may—by example—be mounted to VM 216via connection 234. The additional steps, as discussed in the context ofFIG. 1, may now be performed, e.g., an on-the-fly copy of the compliancerepository volume 208 to a newly—in particular, virtually—requested diskresource. Free space on one of the disk systems 204 and/or 206 may beused for that purpose. For the actual remediation action the compliancerepository volume 208 may then no longer be required. The compliancerepository volume 208 may be shared among all VMs 214, 216, 218 of thehypervisor 210. For the hypervisor 212 a comparable configuration maybeinstalled. Actually, the compliance repository volume 208 may be sharedbetween physical servers 208 using a storage subsystem with dedicatedstorage channels. Such a dedicated storage channel(s) may exist inaddition to normal communication network connections. In case thephysical server 202 may be a PC or similar (see above) not comprising adedicated storage channel, the compliance repository volume 208 may beattached individually to the physical server 208 without using acommunication network, e.g., by using a USB-port or by having thecompliance repository volume 208 as a protected portion of an existingdisk “on board” of the PC.

FIG. 4 shows a block diagram of the method according FIG. 1 in moredetail. Initially, a compliance scan may be performed, 402. A test maybe run, whether or not the related VM may be compliant, 404. In case of“yes”, it may be checked whether the VM is connected to the network,412. In case of “no”, the VM may be connected to the network, 414. Ifthe test 412 results in a “yes”, the system may wait for the nextcompliance scan, 416.

If, in contrast, the test 404 may result in a “no”, the VM may bedisconnected from the network, 406, a compliance repository volume maybe mounted 408, and at least one remediation action may be performed,410. After that, a new compliance scan may be performed, 402. All theseactivities may be controlled by the compliance agent running on the VMensuring compliance control.

FIG. 5 shows an embodiment of a compliance system 500. The compliancesystem 500 for restoring compliance of a VM found to be non-compliant toa compliance rule, may comprise a compliance detection unit 502 adaptedfor detecting non-compliance of a VM with the compliance rule using acompliance agent being deployed on the VM, and a network detaching unit504 adapted for detaching the existing VM from a network.

Moreover, the compliance system 500 may comprise a copy creation unit506 adapted for creating a copy of a compliance repository volume on anewly requested disk resource for the VM, and amounting unit 508 adaptedfor mounting the disk resource having stored the copy of the compliancerepository volume to the VM.

Furthermore, the compliance system—as shown—may comprise an applying 510unit adapted for applying a remediation action to the VM using contentof the copy of the compliance repository volume creating for revertingback the VM to a compliant state, as well as a triggering unit 512adapted for triggering, by the compliance agent, a compliance scan forensuring that the VM complies to the compliance rule. Accordingly, allrequired components may be realized in hardware components.

FIG. 6 shows a block diagram of a computing system 600 with typicalelements also comprising the compliance system 500.

Embodiments of the invention may be implemented together with virtuallyany type of computer, regardless of the platform being suitable forstoring and/or executing program code. For example, as shown in FIG. 6,a computing system 600 may include one or more processor(s) 602 with oneor more cores per processor, associated memory elements 604, an internalstorage device 606 (e.g., a hard disk, an optical drive such as acompact disk drive or digital video disk (DVD) drive, a flash memorystick, a solid-state disk, etc.), and numerous other elements andfunctionalities, typical of today's computers (not shown). The memoryelements 604 may include a main memory, e.g., a random access memory(RAM), employed during actual execution of the program code, and a cachememory, which may provide temporary storage of at least some programcode and/or data in order to reduce the number of times, code and/ordata must be retrieved from a long-term storage medium or external bulkstorage (archive 616) for an execution. Elements inside the computer 600may be linked together by means of a bus system 618 with correspondingadapters. As shown, the system for restoring compliance may be attachedto the bus system 618. The computing system 600 may be a server or a PCor any other mobile device. There may also be an external disk subsystemprovided (not shown) which may be attachable to the computing device,e.g., the compliance repository volume 208. Special adapters may berequired for such an attachment of a storage subsystem comprising disksystems.

The computing system 600 may also include input means, such as akeyboard 608, a pointing device such as a mouse 610, or a microphone(not shown). Alternatively, the computing system may be equipped with atouch sensitive screen as main input device. Furthermore, the computer600, may include output means, such as a monitor or screen 612 [e.g., aliquid crystal display (LCD), a plasma display, a light emitting diodedisplay (LED), or cathode ray tube (CRT) monitor]. The computer system600 may be connected to a network (e.g., a local area network (LAN), awide area network (WAN), such as the Internet or any other similar typeof network, including wireless networks via a network interfaceconnection 614. This may allow a coupling to other computer systems or astorage network or a tape drive. Those, skilled in the art willappreciate that many different types of computer systems exist, and theaforementioned input and output means may take other forms. Generallyspeaking, the computer system 600 may include at least the minimalprocessing, input and/or output means, necessary to practice embodimentsof the invention.

While the invention has been described with respect to a limited numberof embodiments, those skilled in the art, having benefit of thisdisclosure, will appreciate that other embodiments may be devised, whichdo not depart from the scope of the invention, as disclosed herein.Accordingly, the scope of the invention should be limited only by theattached claims. Also, elements described in association with differentembodiments may be combined. It should also be noted that referencesigns in the claims should not be construed as limiting elements.

As will be appreciated by one skilled in the art, aspects of the presentdisclosure may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present disclosure may take theform of an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present disclosure may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that may contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that may communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wire-line, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present disclosure are described with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of thepresent disclosure. It will be understood that each block of theflowchart illustrations and/or block diagrams, and combinations ofblocks in the flowchart illustrations and/or block diagrams, may beimplemented by computer program instructions. These computer programinstructions may be provided to a processor of a general purposecomputer, special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructions,which execute via the processor of the computer or other programmabledata processing apparatus, create means for implementing thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

These computer program instructions may also be stored in a computerreadable medium that may direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions, whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions, which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The block diagrams in the Figures illustrate the architecture,functionality, and operation of possible implementations of systems,methods and computer program products according to various embodimentsof the present disclosure. In this regard, each block in the blockdiagrams may represent a module, segment, or portion of code, whichcomprises one or more executable instructions for implementing thespecified logical function(s). It should also be noted that, in somealternative implementations, the functions discussed hereinabove mayoccur out of the disclosed order. For example, two functions taught insuccession may, in fact, be executed substantially concurrently, or thefunctions may sometimes be executed in the reverse order, depending uponthe functionality involved. It will also be noted that each block of theblock diagrams, and combinations of blocks in the block diagrams, may beimplemented by special purpose hardware-based systems that perform thespecified functions or acts, or combinations of special purpose hardwareand computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to limit of the invention. As usedherein, the singular forms “a”, “an” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or steps plus function elements in the claims below are intendedto include any structure, material, or act for performing the functionin combination with other claimed elements, as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skills in the artwithout departing from the scope and spirit of the invention. Theembodiment was chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skills in the art to understand the invention forvarious embodiments with various modifications, as are suited to theparticular use contemplated.

The invention claimed is:
 1. A method for restoring compliance of avirtual machine found to be non-compliant to a compliance rule, themethod comprising detecting non-compliance of the virtual machine withthe compliance rule using a compliance agent deployed on the virtualmachine; detaching the virtual machine from a network; creating a copyof a compliance repository volume on a requested disk resource for thevirtual machine, wherein the compliance repository volume has storedthereon a version of the virtual machine which adheres to the compliancerule; responsive to detecting the non-compliance of the virtual machine,mounting the requested disk resource, having stored thereon the copy ofthe compliance repository volume, to the virtual machine; responsive tomounting the requested disk resource, applying a remediation action tothe virtual machine using content of the copy of the compliancerepository volume to restore compliance of the virtual machine; andresponsive to applying the remediation action to the virtual machine,triggering, by the compliance agent, a compliance scan to ensure thatthe virtual machine complies with the compliance rule, wherein thecreation of the copy of the compliance repository volume is performed bya storage system controlled by a hypervisor and is triggered by thecompliance agent via the hypervisor.
 2. The method according to claim 1,further comprising: responsive to triggering the compliance scan,detaching the requested disk resource having stored the copy of thecompliance repository volume from the virtual machine.
 3. The methodaccording to claim 1, further comprising: removing the copy of thecompliance repository volume on the requested disk resource.
 4. Themethod according to claim 3, wherein the removing the copy of thecompliance repository volume comprises releasing the requested diskresource.
 5. The method according to claim 1 further comprising:responsive to ensuring that the virtual machine complies with thecompliance rule, attaching the virtual machine back to the network. 6.The method according to claim 2, wherein the detaching of the requesteddisk resource is performed after applying the remediation action.
 7. Themethod according to claim 1, wherein the remediation action is performedby the compliance agent using at least one script and/or at least onesoftware component stored on the copy of the compliance repositoryvolume.
 8. A data processing program for execution in a data processingsystem, the data processing program comprising software code portionsstored in a memory device for performing the method according to claim 1when said data processing program is run on the data processing system.9. The method according to claim 1, wherein the compliance repositoryvolume comprises a storage volume having stored thereon a version of acompliant virtual machine that is compliant with the compliance rule,and the step of applying the remediation action to the virtual machinereverts the virtual machine back to a compliant state.
 10. The methodaccording to claim 9, wherein the compliance repository volume is copiedon-the-fly during operation of the virtual machine to a disk resourcerequested by the compliance agent via the hypervisor in order to createthe copy of the compliance repository volume.
 11. The method accordingto claim 10, wherein the copy of the compliance repository volume iscopied by a storage system such that the copy is performed independentfrom the virtual machine.
 12. A compliance system adapted to restorecompliance of a virtual machine found to be non-compliant to acompliance rule, the compliance system comprising: a compliancedetection unit adapted for detecting non-compliance of a virtual machinewith the compliance rule using a compliance agent deployed on thevirtual machine; a network detaching unit adapted to detach the virtualmachine from a network; a copy creation unit adapted to create a copy ofa compliance repository volume on a requested disk resource for thevirtual machine, wherein the compliance repository volume has storedthereon a version of the virtual machine which adheres to the compliancerule; a mounting unit adapted to mount, responsive to detecting thenon-compliance of the virtual machine, the requested disk resource,having stored thereon the copy of the compliance repository volume, tothe virtual machine; an applying unit adapted to apply, responsive tomounting the requested disk resource, a remediation action to thevirtual machine using content of the copy of the compliance repositoryvolume to revert the virtual machine back to a compliant state; and atriggering unit adapted to trigger by the compliance agent, responsiveto applying the remediation action to the virtual machine, a compliancescan to ensure that the virtual machine complies to the compliance rule,wherein the creation of the copy of the compliance repository volume isperformed by a storage system controlled by a hypervisor and istriggered by the compliance agent via the hypervisor.
 13. A computersystem comprising a central processing unit, a memory, and thecompliance system according to claim
 12. 14. The compliance systemaccording to claim 12, wherein the compliance repository volumecomprises a storage volume having stored thereon a version of acompliant virtual machine that is compliant with the compliance rule,and the step of applying the remediation action to the virtual machinereverts the virtual machine back to a compliant state.
 15. A computerprogram product stored on a non-transitory computer usable medium,comprising computer readable program code for causing a computer toperform steps of: detecting non-compliance of the virtual machine withthe compliance rule using a compliance agent deployed on the virtualmachine; detaching the virtual machine from a network; creating a copyof a compliance repository volume on a requested disk resource for thevirtual machine, wherein the compliance repository volume has storedthereon a version of the virtual machine which adheres to the compliancerule; responsive to detecting the non-compliance of the virtual machine,mounting the requested disk resource, having stored thereon the copy ofthe compliance repository volume, to the virtual machine; responsive tomounting the requested disk resource, applying a remediation action tothe virtual machine using content of the copy of the compliancerepository volume to restore compliance of the virtual machine; andresponsive to applying the remediation action to the virtual machine,triggering, by the compliance agent, a compliance scan to ensure thatthe virtual machine complies with the compliance rule, wherein thecreation of the copy of the compliance repository volume is performed bya storage system controlled by a hypervisor and is triggered by thecompliance agent via the hypervisor.
 16. The computer program productaccording to claim 15, wherein the compliance repository volumecomprises a storage volume having stored thereon a version of acompliant virtual machine that is compliant with the compliance rule,and the step of applying the remediation action to the virtual machinereverts the virtual machine back to a compliant state.